Automated story generation

ABSTRACT

Automatic story production is implemented by the utilization of theme scripts with user assets to generate a quality finished product with minimum user input or direction. A user chooses a predesigned theme script to be applied to the user&#39;s assets to automatically create a story with a particular look and feel. Metadata and feature information, when available, is automatically gathered from the user assets to personalize the generated story. A user can include additional information and/or alter any aspect of the generated story to further personalize the resultant finished product.

BACKGROUND

Users can create stories, e.g., movies, from user assets such as userimages, videos, and audio files. Users can use a computing device torender individual manipulations for combining, grouping and ordering aset of user assets for output presentation. The generated movies can bedesirable for showcasing the user assets.

With the plethora of media and messages vying for individuals'attentions via their computers, televisions, cell phones, radios, etc,what can assist any particular presentation to stand out to an audience,along with the story subject, is the caliber of polish with which thestory is generated.

Users have to commit time and effort to create a story from their userassets as there can be many factors and elements a user will contendwith in generating a finished product. Additionally, creating a finishedproduct from a set of user assets can require users to have the skills,artistic talent and knowledge of the software for implementing thedetails to generate the intended resultant product.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key or essentialfeatures of the claimed subject matter, nor is it intended to be used asan aid in determining the scope of the claimed subject matter.

Embodiments discussed herein include systems and methodology forenabling automatic and personalized user story creation.

In embodiments user content, or assets, e.g., images, video and/or audiofiles, are automatically analyzed and organized within a user story,e.g., a movie. In embodiments rules of a theme script that is designedto create a particular feeling or theme for a finished user story areautomatically applied to user assets to create a predesigned look forthe user assets which become elements of the generated user story.

In embodiments an introduction section and an end section for the userstory are automatically created pursuant to theme script rules and usinguser assets, metadata and/or feature information mined from analyzeduser assets.

In embodiments the user story is automatically organized into chapterspursuant to theme script rules and the nature and quantity of the userassets.

In embodiments the user story is personalized by the inclusion ofcaptions that are automatically generated from information mined fromanalyzed user assets and/or are automatically generated with generictext that can be replaced by user input when the necessary assetinformation is unavailable or nonexistent.

In embodiments various treatments, e.g., transitions, effects, musicinclusions, titles, credits, caption designs, etc., are applied to orgenerated for elements of the user story pursuant to theme script rules.In an aspect of these embodiments the treatments are intended to helpcreate a personalized user story with a particular look and feel.

In embodiments elements of the automatically generated user story can bemodified by a user to further enhance the personalization of the finaluser story. In embodiments a finalized user story can be stored and/orpublished, e.g., to one or more websites, one or more devices, e.g.,cell phones, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features will now be described with reference to thedrawings of certain embodiments and examples which are intended toillustrate and not to limit, and in which:

FIG. 1 depicts an embodiment movie production system that automaticallytransforms and arranges user content to generate a story.

FIG. 2 depicts sections of an embodiment generated story.

FIG. 3 depicts embodiment theme script rule groups.

FIGS. 4A-4B illustrate an embodiment logic flow for an embodiment movieproduction system.

FIGS. 5A-5E illustrate an embodiment logic flow for an embodiment movieproduction system to execute a user-chosen theme script to generate astory.

FIG. 6 is a block diagram of an exemplary basic computing device systemthat can process software, i.e., program code, or instructions.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of embodiments described herein. It will be apparent,however, to one skilled in the art that the embodiments may be practicedwithout these specific details. In other instances well-known structuresand devices are either simply referenced or shown in block diagram formin order to avoid unnecessary obscuration. Any and all titles usedthroughout are for ease of explanation only and are not for any limitinguse.

FIG. 1 depicts an embodiment movie production system 100 that takes asinput user content 135, or user assets 135, and arranges the usercontent 135 to generate a personal story, e.g., movie, 160 with highquality and minimum user effort. In embodiments user content 135 caninclude, but is not limited to, user images 105, user video 115, alsoreferred to herein as video clips, user audio 125, user graphics and/oruser text files. In an embodiment the user assets 135 are each composedof one or more frames; i.e., one or more images in a set of images 105,one or more stills in a video 115, one or more predefined timed segmentsof an audio file 125, etc.

In an embodiment the product, e.g., movie, 160 generated by the movieproduction system 100 is a resultant story that is told by the userassets 135 included therein along with any dynamically generatedelements 155, e.g., a scrapbook page of selected user images 105, etc.,and preselected elements, e.g., clipart, music, etc. As used herein, theterm movie is intended to refer to any product, or story, generated byan embodiment movie production system 100 using user assets 135. In anembodiment a movie 160 consists of a collection of one or more frameswherein each frame can be, or consist of, a user asset, a modified userasset, a dynamically generated element 155, predefined content, etc., ora combination thereof, etc.

In an embodiment the movie 160 generated by the movie production system100 can have three sections, as depicted in FIG. 2. An embodiment firstmovie section is an intro, or introduction, section 210. In anembodiment an intro section 210 is a section added to the beginning ofthe movie 160 that introduces the movie 160. In an aspect of thisembodiment an intro section 210 can include one or more titles, one ormore credits, date information, user content 135 information, one ormore phrases, e.g., lyrics to a song, words from a poem, captions, etc.In an aspect of this embodiment an intro section 210 can also, oralternatively, include content 155, or elements 155, that is dynamicallygenerated from user content 135; e.g., a collage formed from usersassets 135.

An embodiment second movie section is the mid, or body, section 220. Inan embodiment the mid section 220 is the section of the movie 160 thatis the story produced from the user assets 135. In an embodiment the midsection 220 includes user assets 135, unaltered, transformed, editedand/or modified. In an embodiment the mid section 220 can also, oralternatively, include elements 155 dynamically generated from userassets 135, e.g., a collage of images 105 arranged on a predesignedbackground, frame captions created from mined metadata, etc. In anembodiment frames of the mid section 220 of the movie 160 can also, oralternatively, include predefined content; e.g., a music score, clipart, etc.

An embodiment third movie section is the outro, or end, section 230. Inan embodiment an end section 230 is a section added to the end of themovie 160 that concludes the movie 160. In an aspect of this embodimentan end section 230 can include one or more titles, one or more credits,date information, user content 135 information, one or more phrases,e.g., lyrics to a song, words from a poem, captions, etc. In an aspectof this embodiment an end section 230 can also, or alternatively,include elements 155 dynamically generated from user content 135.

In an embodiment the mid section 220 of a movie 160 can be divided intotwo or more chapters, or sections, 240, each with its own subject, orcontent, or sub-theme. In this embodiment each chapter 240 has a midsection 220. In an aspect of this embodiment each chapter 240 can alsoinclude an intro section 210. In an aspect of this embodiment eachchapter 240 can also, or alternatively, include an end section 230.

In embodiments a movie 160 can consist of just a mid section 220, anintro section 210 and a mid section 220, a mid section 220 and an endsection 230, or an intro section 210, a mid section 220 and an endsection 230.

Referring back to FIG. 1, in an embodiment theme scripts, or scriptfiles, 150 of the movie production system 100 are designed to createstories, e.g., movies, 160 from user assets 135. In an embodiment thetheme scripts 150 are generated with creative input from one or moreartists and/or one or more graphic designers who choose harmoniousstyling elements for a particular theme. In an embodiment theme scripts150 can also, or alternatively, be generated by a user 145 or any onedesiring to author a script file 150. In an embodiment theme scripts 150can also, or alternatively, be generated by the execution of scriptdesign software.

In an embodiment the theme scripts 150 are in a human-readable formatwhich provides for efficient maintenance and flexible modification of atheme script 150.

An embodiment theme application engine 120 of a movie production system100 has the capability to utilize a user chosen theme script 150 toautomatically arrange and transform user assets 135 in such a way thatthe resultant story, or movie, 160 is of a user-perceived high qualitywith minimal user effort required. In an embodiment the themeapplication engine 120 runs a theme script 150 against user assets 135to create a story, or movie, 160. In an embodiment each theme script 150contains information, or rules 175, on how the user assets 135 should befiltered, arranged and/or transformed (visually and/or audioally) tocreate a movie 160 with a particular theme. In an embodiment a themerefers to a mood, an aesthetic style or an event, e.g., joyous, sporty,birthday, wedding, sepia, colorful, etc. In an embodiment theme scripts150 provide an abstract mechanism for defining how an end product, e.g.,movie 160, should look and sound without the need to know any details ofthe user assets 135.

In an embodiment, before a theme is applied to a set of user assets 135metadata and feature information is mined from the user content 135;e.g., any tags related to the user content 135, any tags identifyingpeople in the user content 135, any tags identifying the location of thepictured user content 135; feature information on where faces arelocated in a frame of user content 135, etc. Mining some of thisinformation can be computationally expensive and time consuming. Thus,in an embodiment the mining of metadata and feature information fromuser content 135 is done in the background when the user content 135 isfirst input, or made available, to the movie production system 100.

In an embodiment, when user content 135 is input to the movie productionsystem 100 it is automatically fed through an embodiment metadatafeature extraction and analysis engine 110, also referred to herein asan analysis engine 110. In an embodiment the analysis engine 110executes asynchronously in the background using spare CPU cycles. In anembodiment the analysis engine 110 has the capability to extract,analyze and store metadata and feature information from user content 135that can be used later by an embodiment theme application engine 120 increating a personal movie 160. In an embodiment the analysis engine 110stores the mined metadata and feature information in one or moremetadata databases 130. In other embodiments mined metadata and featureinformation is stored and referenced by one or more of a variety ofstorage constructs, including but not limited to, metadata databases130, tables, lists, linked lists, etc.

In an embodiment, before a theme is applied to a set of user assets 135one or more analyses are performed on the user assets 135. In anembodiment the analyses performed can include statistical analysis todetermine how much is changing over x frames in a user video 115 or useraudio file 125; e.g., how much action is occurring over x frames of auser video 115. In an embodiment the analyses performed can include adetermination of the loudness of the audio portion of a user video 115or subset of the user video 115 or the loudness of a user audio file 125or subset of a user audio file 125. In an embodiment the analysesperformed can include a determination of the clarity of one or more userimages 105 and/or one or more frames of a user video 115; i.e., adetermination of how in focus one or more user images 105 and/or one ormore user video frames are. In an embodiment the analyses performed caninclude a determination of whether one or more images 105 and/or one ormore frames of a user video 115 have red-eye. In embodiments a varietyof additional and/or different analyses can be performed on a set ofuser assets 135. In an embodiment information derived from one or moreanalyses, also referred to herein as asset modification information ordetails, can be used to identify modifications, or corrections, that canbe made to one or more user assets 135; e.g., modifications for red-eye,modifications for out-of-focus user images 105 or frames of a user videoclip 115, etc.

In an embodiment the analysis engine 110 has the capability to performanalyses on a set of user assets 135. Analyses of the user assets 135can be computationally expensive and time consuming. Thus, in anembodiment the analyses of the user content 135 is done in thebackground when the user content 135 is first input to the movieproduction system 100. In an embodiment, when user content 135 is inputto the movie production system 100 it is automatically fed through anembodiment analysis engine 110. In an embodiment the analysis engine 110executes asynchronously in the background using spare CPU cycles toperform analyses on the user content 135.

In an embodiment movie production system 100 an adaptation engine 140has the capability to use asset modification information from theanalysis engine 110 to modify, or correct, one or more user assets 135.For example, the adaptation engine 140 corrects red eyes, adjustslighting and exposure, shortens or otherwise segments a video 115 forspecific content and/or to reduce duplicity or redundancy, deletes ormodifies out-of-focus frames in a video 115, etc. In an embodiment theresultant modified user asset(s) are stored in one or more assetdatabases 170. In other embodiments modified user assets are stored andreferenced by one or more of a variety of storage constructs, includingbut not limited to, asset databases 170, tables, lists, linked lists,etc. In this manner the user assets 135 remain as inputted and areunaltered by the embodiment movie production system 100 and the movieproduction system 100 is non destructive to user content 135.

In an embodiment the adaptation engine 140 has the capability to takedirections from the theme application engine 120 and apply theme scriptrules 175 to user assets 135. For example, the adaptation engine 140 cancrop one or more user images 105 as directed by one or more theme scriptrules 175 to zoom in on a particular image feature; e.g., a person, ageographic feature, e.g., mountain or river, etc. As another example theadaptation engine 140 can impose an effect on user assets 135; e.g.,transpose user assets 135 to black-and-white, fade in or fade out on oneor more user asset frames, etc. In an embodiment the resultant modifieduser asset(s) are stored in one or more asset databases 170. In otherembodiments modified user assets are stored and referenced by one ormore of a variety of storage constructs, including but not limited to,asset databases 170, tables, lists, linked lists, etc. In this mannerthe original user assets 135 remain unaltered by the embodiment movieproduction system 100.

As noted, in an embodiment each theme script 150 contains rules 175 thatdefine the movie 160 to be generated. In an embodiment each theme script150 has rules 175 that, when applied, create the format of the movie160, e.g., size of the mid section 220, number and ordering of chapters240 in the mid section 220, etc. In an embodiment each theme script 150contains rules 175 for the contents of any intro section(s) 210, thecontents of the mid section 220, and the contents of any end section(s)230.

In an embodiment each theme script 150 can contain rules 175 to beapplied to user assets 135 to generate transformations on one or moreuser assets 135 by, e.g., correlating metadata and feature informationmined from or otherwise related to the user assets 135 with the themescript rules 175. In this manner user assets 135 can be transposed tosuit the theme of the selected script file 150; e.g., user assets 135can be modified to be black-and-white, cropped to depict specificcontent, etc.

In an embodiment each theme script 150 can contain rules 175 thatidentify special keywords that can be replaced with metadata or featureinformation extracted from the user assets 135, e.g., names identifyingfaces of people in the images 105 and/or video 115, location featureidentification information, e.g., mountain range, waterfall, etc., inthe images 105 and/or video 115, etc. In this manner the generated movie160 is rendered personal to the user 145 in accordance with the userassets 135.

In an embodiment the theme scripts 150 can have as a target a number ofuser assets 135 or range of a number of user assets 135. In anembodiment the theme scripts 150 can accommodate a smaller number ofuser assets 135 than targeted. An embodiment theme script 150 targetedto accommodate more than the existing number of user assets 135 canreuse user assets 135 among the frames of the generated movie 160 in anorderly or random pattern in order to generate a movie 160 with asufficient desired length. An embodiment theme script 150 targeted toaccommodate more than the existing number of user assets 135 can spreadthe existing user assets 135 among the frames of the generated movie 160in such a manner as to include duplicative user assets 135 but withdiffering treatments, e.g., effects, transitions, etc., in order togenerate a movie 160 with a sufficient desired length. In an aspect ofthese embodiments a theme script 150 will generate a mid section 220 ofa movie 160 that has more frames than user assets 135.

An embodiment theme script 150 targeted to accommodate more than theexisting number of user assets 135 can generate a shorter play-lengthmovie 160 that coincides with the existing user asset set. An embodimenttheme script 150 targeted to accommodate more than the existing numberof user assets 135 can increase the time spent on one or more userassets 135 included in frames in the movie 160 to generate a movie 160of a predetermined play-length or within a predetermined play-lengthtime span. An embodiment theme script 150 targeted to accommodate morethan the existing number of user assets 135 can create frames of a movie160 by dynamically generating elements 155 to be included in the movie160 from the user assets 135, e.g., generating additional images fromuser asset video clips 115 and/or portions of user asset images 105,generating additional video clips by dividing existing user asset videoclips 115 into smaller play-length videos, generating scrapbook pageswith user assets 135, etc. In other embodiments theme scripts 150targeted to accommodate more than the existing number of user assets 135can manage a smaller set of user assets 135 with a combination of one ormore of these embodiment approaches and/or with other approaches.

In an embodiment the theme scripts 150 can manage a larger number ofuser assets 135 than are targeted to be accommodated in a movie 160. Anembodiment theme script 150 targeted to accommodate less than theexisting number of user assets 135 can determine not to include all theuser assets 135 in the movie 160. An embodiment theme script 150targeted to accommodate less than the existing number of user assets 135can include additional chapters 240, longer chapters 240, a longer midsection 220, etc. in the generated movie 160 to manage all or a largersubset of the user assets 135 than targeted for. An embodiment themescript 150 targeted to accommodate less than the existing number of userassets 135 can shorten the frame display time for one or more of theuser assets 135 and/or speed up the output of one or more user assetvideo clips 115 included in the generated movie 160. In otherembodiments theme scripts 150 targeted to accommodate less than theexisting number of user assets 135 can manage a larger set of userassets 135 with a combination of one or more of these embodimentapproaches and/or with other approaches.

In an embodiment a theme script 150 can contain rules 175 for the themeapplication engine 120 to apply to dynamically generate elements 155 forthe movie 160. Such dynamically generated elements 155 can include, butare not limited to, frame background designs, scrapbook pages, collages,additional images generated from still frames of a user asset video 115,additional images generated from differing regions of a user asset image105, etc. In an embodiment dynamically generated elements 155 are storedin one or more movie asset databases 195. In other embodimentsdynamically generated elements 155 are stored and referenced by one ormore of a variety of storage constructs, including but not limited to,movie asset databases 195, tables, lists, linked lists, etc.

In an embodiment a theme script 150 can contain rules 175 for the themeapplication engine 120 to apply for the inclusion of predefined contentwithin the movie 160. Such additional predefined content can include,but is not limited to, clip art, audio tracks, caption style, etc.

In an embodiment there are various groups of theme script rules 175 toeffect a variety of resultant content, or elements, included in agenerated movie 160. Each theme script 150 can contain rules 175 fromone or more of these groups which are selected and/or tailored to definea portion of the resultant movie 160 with the identified theme from thetheme script 150.

FIG. 3 depicts embodiment theme script rule groups 300. A grouping rule,or rules, 305 in an embodiment script file 150 defines the logic bywhich different user assets 135 are to be grouped into chapters, orsections, of the movie 160; e.g., by content location, date range, theidentity of the people appearing in the user assets 135, random, etc. Anaspect of this grouping rule(s) 305 also defines the size of thechapters 240 or sections; i.e., how much user content 135 is to beincluded in any particular chapter 240 and/or how much time each chapter240 in the movie 160 should play, or run.

An ordering rule, or rules, 310 in an embodiment script file 150 definesthe logic by which different user assets 135 are to be ordered withinthe movie 160; e.g., by ascending or descending time properties,randomly, etc. In an embodiment the ordering rule(s) 310 define theorder of user assets 135 for the chapters 240 of the movie 160 and/orthe order of user assets 135 within the movie 160.

A selection rule, or rules, 315 in an embodiment script file 150 managesduplicative user assets 135 and the omission of user assets 135 from theresultant movie 160, including the omission of one or more images 105from a set of images 105 and/or the trimming of user video 115 and/oraudio files 125. In an embodiment the omission of user assets 135 fromthe movie 160 can be for a variety of results including the reduction ofduplicative views or sounds within the movie 160, the inclusion ofselective content within the movie 160, maintenance of a predefined playtime for the movie 160, etc.

An aspect of embodiment selection rule(s) 315 defines, or otherwisedetermines, how many frames of which user assets 135 are to be includedin the movie 160. In an embodiment this aspect of the selection rule(s)315 defines which, if any, duplicative frames, from a contentperspective, of the user assets 135 are to be included in the movie 160.For example, there may be ten (10) images of the same person in the samepose with the same location background in a set of user images 105 andthe selection rule(s) 315 define a maximum of two (2) images that depictthe same subject matter are to be included in the movie 160. In anembodiment selection rule(s) 315 also define which two of the ten imagesare to be included in the movie 160, e.g., the first two images in theset of images 105, the two images in the set of images 105 with the faceof the depicted person most centered, etc.

A transition rule, or rules, 320 in an embodiment script file 150defines the transitions to be imposed on the user assets 135 and otherelements 155 included in each chapter 240 and the movie 160; e.g., zoom,pan, rotate, fade in, fade out, etc.

An effects rule, or rules, 325 in an embodiment script file 150 definesthe effects to be imposed on the user assets 135 and other elements 155included in the movie 160; e.g., render one or more images 105black-and-white, render one or more images 105 sepia, mute audio in oneor more chapters 240, etc.

An intro rule, or rules, 330 in an embodiment script file 150 definesthe information to be used to create an intro section 210 for the movie160. In an embodiment an intro rule(s) 330 also, or alternatively,defines the information for generating an intro section 210 for one ormore chapters 240 of the movie 160. As noted, in an embodiment an introsection 210 is a special section added to the beginning of the movie 160and/or the beginning of a movie chapter 240. In an embodiment thecontent of an intro section 210 includes the look, feel and/or audio foreach frame of the intro section 210; e.g., black backdrop with whiteletters and a voice over from frames of a video 115, etc.

In an embodiment the content of an intro section 210 can contain one ormore titles, one or more credits, date information, content information,one or more phrases, e.g., lyrics to a song, words from a poem,captions, etc. In an embodiment the content of an intro section 210 canalso, or alternatively, be content 155 that is dynamically generatedfrom user content 135.

In an embodiment content of an intro section 210 is automaticallygenerated from existing metadata and/or feature information mined fromuser assets 135; e.g., titles extracted from image tags, names extractedfrom image tags, etc. In an embodiment content of an intro section 210is also, or alternatively, generated from prompted user input when thenecessary metadata and/or feature information is unavailable to themovie production system 100. In an embodiment content of an introsection 210 is also, or alternatively, generated from preexistingnon-user asset content; e.g., phrases from music lyrics and/or poems,clip art, a music selection, etc.

In an embodiment titles, credits or captions can already exist in one ormore frames of an intro section 210 because, e.g., the user 145 haspreviously caused a movie 160 to be generated from a set of user assets135 and the user 145 has subsequently changed the theme script 150 to beapplied to the same set of user assets 135, the user has previouslycreated titles, credits or captions associated with one or more userassets 135 included in an introduction section 210 or one or more framesof an introduction section 210, etc. In an aspect of this embodiment thetext of the existing titles, credits and captions will not be removed orreplaced pursuant to theme script rules 175. In an aspect of thisembodiment the effect and/or transition applied to the text of theexisting titles, credits and captions of the introduction section(s) 210will be altered as dictated by one or more theme script rules 175defining the text style for the resultant movie introduction section(s)210.

An outro rule, or rules, 335 in an embodiment script file 150 definesthe information to be used to create an end, or outro, section 230 forthe movie 160. In an embodiment an outro rule(s) 335 also, oralternatively, defines the information for generating an end section 230for each chapter 240 of the movie 160. As noted, in an embodiment an endsection 230 is a special section added to the end of the movie 160and/or the end of one or more movie chapters 240. In an embodiment thecontent of an end section 230 includes the look, feel and/or audio foreach frame of the end section 230; e.g., slow fade out of image framefrom user image 105 overlaid with black lettering and enhanced with amusical selection, etc.

In an embodiment the content of an end section 230 can contain one ormore titles, one or more credits, date information, content information,one or more phrases, e.g., lyrics to a song, words from a poem,captions, etc. In an embodiment the content of an end section 230 canalso, or alternatively, be elements 155 dynamically generated from usercontent 135; e.g., a collage formed from user assets 135.

In an embodiment content of an end section 230 is automaticallygenerated from existing metadata and/or feature information mined fromuser assets 135; e.g., credits extracted from image tags, etc. In anembodiment content of an end section 230 is also, or alternatively,generated from prompted user input when the necessary metadata and/orfeature information is unavailable to the movie production system 100.In an embodiment content of an end section 230 is also, oralternatively, generated from preexisting non-user asset content; e.g.,phrases from music lyrics and/or poems, clip art, a music selection,etc.

In an embodiment titles, credits or captions can already exist in one ormore frames of an end section 230 because, e.g., the user 145 haspreviously caused a movie 160 to be generated from a set of user assets135 and the user 145 has subsequently changed the theme script 150 to beapplied to the same set of user assets 135, the user has previouslycreated titles, credits or captions associated with one or more userassets 135 included in an end section 230 or one or more frames of anend section 230, etc. In an aspect of this embodiment the text of theexisting titles, credits and captions will not be removed or replacedpursuant to theme script rules 175. In an aspect of this embodiment theeffect and/or transition applied to the text of the existing titles,credits and captions of the end section(s) 230 will be altered asdictated by one or more theme script rules 175 defining the text stylefor the resultant movie end section(s) 230.

Caption rules 340 in an embodiment script file 150 define how and wherecaptions are to be added to user assets 135 and/or frames of the movie160. In an embodiment caption rules 340 further contain the details onthe style and treatment of various captions included within the movie160; e.g., font, color, size, position, effect, etc.

In an embodiment caption rules 340 can contain special keywords that aresubsequently replaced by appropriate metadata and/or feature informationpreviously mined from the user assets 135. In an embodiment, if themetadata or feature information necessary to personalize a caption isunavailable the caption will be generated with generic text and the user145 will be prompted to thereafter provide input to replace the generictext and render the movie 160 specific and/or personal.

In an embodiment captions can already exist in one or more frames of themovie 160 because, e.g., the user 145 has previously caused a movie 160to be generated from a set of user assets 135 and the user 145 hassubsequently changed the theme script 150 to be applied to the same setof user assets 135, the user has previously created captions associatedwith one or more user assets 135 included in the movie 160, etc. In anaspect of this embodiment the text of the existing captions will not beremoved or replaced pursuant to theme script rules 175. In an aspect ofthis embodiment the effect and/or transition applied to the text of theexisting captions will be altered as dictated by one or more themescript rules 175 defining the text style for the resultant moviecaptions. Thus, in an aspect of this embodiment caption text positioningand duration is not guaranteed with the application of a new themescript 150 to the user assets 135 as the new theme script 150 may needto modify these to account for, e.g., animation, theme aesthetics, etc.

An art rule, or rules, 345 in an embodiment script file 150 defines howany included art, e.g., clip art, etc., should be added to, orotherwise, utilized, in the movie 160; e.g., the addition of adornmentssuch as backgrounds or clip art images to one or more movie frames, etc.In an embodiment the art rule(s) 345 details how user assets 135 are toappear with or within added clip art in one or more movie frames; e.g.,a scrapbook page with user asset images 105 positioned within clip artframes, etc.

In an embodiment one or more theme scripts 150 identify one or moremusic scores, via a music rule, or rules, 350 to be included within themovie 160. In an aspect of this embodiment the identified music score(s)are intended to enhance the theme, or mood, of the chosen script file150 and, therefore, the resultant movie 160. In an embodiment the musicrules 350 include directions for the positioning of the music within themovie 160 and the treatment, e.g., volume, and effects, e.g., fade in,fade out, loop, etc., to be imposed on the included music.

In an embodiment the music rules 350 also, or alternatively, dictate howa user's audio 120 is to be managed within the movie 160; e.g., playedwith specific chapters and muted for others, softened and playedthroughout the body 220 of the movie 160, played in the introduction 210and end 230 sections of the movie 160, etc.

In an embodiment if there is user-specified music already associatedwith one or more user assets 135 or one or more frames of the movie 160then the user 145 is asked to indicate whether they wish to retain theuser-specified music or utilize the theme script identified music. In analternative embodiment if there is user-specified music associated withone or more user assets 135 or one or more frames of the movie 160 thenthe user 145 is notified that the user-specified music will not beimplemented and the theme script identified music is included within themovie 160 pursuant to one or more music rules 350. In a secondalternative embodiment if there is user-specified music associated withone or more user assets 135 or one or more frames of the movie 160 thenthe user-specified music is retained and used for the movie 160.

In an embodiment if there is no music associated with the user assets135 or frames of the movie 160 then the user 145 is prompted, via the UI180, to select, or otherwise identify, a music selection, or selections,to be included within the movie 160. In an alternative embodiment ifthere is no music associated with the user assets 135 or frames of themovie 160 then pre-identified music indicated in one or more themescript rules 175 is used for the movie 160.

In an embodiment a dynamic frame generation rule(s) 355 in a script file150 defines how elements 155, or frames, are to be dynamically createdfor incorporation within the movie 160. Dynamically generated elements155 can include, but are not limited to, frame background designs,scrapbook pages, collages, additional images generated from still framesof a user asset video 115, additional images generated from differingregions of a user asset image 105, etc. For example, a dynamic framegeneration rule(s) 355 can define the creation of a scrapbook page framewith user images 105 arranged about the frame and decorated withpre-selected clipart to be included within the movie 160. As a secondexample, a dynamic frame generation rule(s) 355 can define thegeneration of two images from one user asset image 105 where each of thetwo generated images depict differing regions, or subjects, e.g.,different people, etc., within the user asset image 105. In an aspect ofthis embodiment mined metadata and feature information and/or theresults of analyses performed on the original user asset 135 is used inconjunction with, or by, the dynamic frame generation rule(s) 355 todynamically generate elements 155 for the movie 160 from existing userassets 135.

In an embodiment dynamically generated elements 155 created pursuant toone or more dynamic frame generation rules 355 are stored in one or moremovie asset databases 195. In other embodiments dynamically generatedelements 155 are stored and referenced by one or more of a variety ofstorage constructs, including but not limited to, movie asset databases195, tables, lists, linked lists, etc.

In an embodiment a dynamic frame generation rule(s) 355 controls theplacement of dynamically generated elements 155 within the movie 160;e.g., first frame in the intro section 210, etc. In an embodiment adynamic frame generation rule(s) 355 defines the transitions and effectsto be implemented for dynamically generated elements 155. In an aspectof this embodiment the transitions and effects identified by a dynamicframe generation rule 355 supersedes any transition rules 320 or effectsrules 235 in the script file 150 that would otherwise be implemented forthe dynamically generated element 155 due to, e.g., its position withinthe movie 160.

In embodiments more, less and/or alternative groups 300 of theme scriptrules 175 exist.

Referring again to FIG. 1, in an embodiment a user 145 interacts withthe movie production system 100 via a user interface, UI, 180. In anembodiment the user 145 enables user content 135 to be input, orotherwise made accessible, to the computing system, or device, e.g.,personal computer, computer network, etc. hosting, or otherwise running,the movie production system 100. In an embodiment the theme applicationengine 120, via the UI 180, prompts the user 145 for input to render themovie 160 more polished and personal. In an embodiment the UI outputsthe movie 160 to the user 145 for review. In an embodiment the user 145can make changes to the movie 160 via the UI 180.

In an embodiment, while the movie production system 100 is generating amovie 160 a progress dialog box is displayed to the user 145 via the UI180. In an embodiment the progress dialog box indicates the actioncurrently being performed to generate the movie 160; e.g., applyingblack-and-white movie theme, generating intro section, etc. In anembodiment the progress dialog box indicates how much of the moviegeneration has been completed; e.g., 60% complete, etc.

In an embodiment a progress dialog box is displayed to a user 145 onlywhen the movie production system 100 requires a user perceptible time toapply the rules 175 of a theme script 150 to generate a movie 160

In an embodiment the user 145 can, via the UI 180, inform the movieproduction system 100 that the movie 160 is finished and/or ready forpublication. In an embodiment the movie production system 100 encodes afinished movie 160 in one or more predefined formats and/or one or moreuser-specified formats and/or one or more formats supported by a storagemedia associated with the movie production system 100 and upon which thefinished movie 160 will be stored and/or pushed to and/or published to.In an embodiment there can be more than one copy of a finished, encodedmovie 190, also referred to herein as the published movie 190. In anembodiment the movie production system 100 stores each encoded versionof the finished movie 190 to one or more storage media, e.g., harddrive, computer memory, DVD, CD, memory stick, etc.

In an embodiment the movie production system 100 can publish a finished,encoded version of the movie 190 by pushing, or otherwise storing, thepublished movie 190 to one or more devices or media 185, e.g., computer,cell phone, etc. In an embodiment the movie production system 100 canpublish a finished, encoded version of the movie 190 to one or morepublication points 165, e.g., websites, email addresses, etc.

FIGS. 4A-4B illustrate an embodiment logic flow for an embodiment movieproduction system 100. While the following discussion is made withrespect to systems portrayed herein the operations described may beimplemented in other systems. The operations described herein are notlimited to the order shown. Additionally, in other alternativeembodiments more or fewer operations may be performed. Further, theoperations depicted may be performed by an embodiment movie productionsystem 100 or by an embodiment movie production system 100 incombination with one or more other systems.

Referring to FIG. 4A, in an embodiment user assets are introduced, orotherwise made available to, the movie production system 400.

In an embodiment the movie production system analyzes the user assets tomine metadata and feature information 402. In an embodiment the movieproduction system stores metadata and feature information collected fromuser assets in one or more metadata databases 404. In an aspect of theseembodiments the analysis engine 110 of the movie production system 100has the capability to analyze the user assets 135 to mine metadata andfeature information and to store the mined data and information in oneor more metadata databases 130. In alternative aspects of theseembodiments the analysis engine 110 stores mined metadata and featureinformation which is referenced by one or more of a variety of storageconstructs, including but not limited to, metadata databases 195,tables, lists, linked lists, etc.

In an embodiment the movie production system analyzes the user assets toidentify user assets or user asset portions, i.e., frames or segments,to be modified, e.g., to correct red-eye, etc., 406. In an aspect ofthis embodiment the analysis engine 110 of the movie production system100 has the capability to analyze user assets 135 to identify those userassets 135, or portions of user assets 135, to be modified or corrected.In this aspect of this embodiment the analysis engine 110 notifies theadaptation engine 140 of the movie production system 100 to modify theuser assets 135 so identified.

In an embodiment the movie production system makes any identifiedmodifications and corrections to indicated user assets 408. In anembodiment the modified user assets are stored 410. In an aspect ofthese embodiments the adaptation engine 140 of the movie productionsystem 100 has the capability to make the modifications and correctionsto the identified user assets 135, or portions thereof, and to store theresultant modified user assets.

In an embodiment, at decision block 412 a determination is made as towhether new user assets have been included by the user after a priormovie version has already been generated for review. If no, in anembodiment the user, via the UI of the movie production system, choosesa theme script to be applied to the user assets, or a user-identifiedsubset of the user assets, 414. In an embodiment the theme applicationengine of the movie production system is apprised of the user selectionand accesses the chosen script file 416.

In an embodiment the movie production system executes, or otherwise actsupon, the chosen script file to generate a story, e.g., a movie, 418. Inan aspect of this embodiment the theme application engine 120 of themovie production system 100 has the capability to execute theuser-chosen script file 150 to generate a movie 160. In an aspect ofthis embodiment the theme application engine 120 applies rules 175 ofthe user-chosen script file 150 to one or more user assets 135, one ormore modified user assets and/or one or more generated elements 155.Additional details for this embodiment step 418 are described withreference to FIGS. 5A-5E.

In an embodiment the generated story, e.g., movie, is output to the userfor review 420. In an aspect of this embodiment the theme applicationengine 120 of the movie maker system 100 directs the output of the movie160 to the user 145 via the UI 180. In an embodiment the movie 160 is ina WYSIWYG (what-you-see-is-what-you-get) format appropriate for userreview.

In an embodiment at decision block 422 a determination is made as towhether the user has made a theme change request. If yes, in anembodiment the theme application engine of the movie production systemis apprised of the user selection and accesses the newly chosen scriptfile 416.

Referring to FIG. 4B, at decision block 430 a determination is made asto whether the user has requested any edits to the movie. In anembodiment a user 145 can override one or more theme script rules 175and/or add additional elements or content, e.g., transitions or effectsnot accounted for by the theme script 150, to the movie 160 byrequesting edits to the movie 160 via the UI 180. For example the user145 can choose different transitions and/or effects, add pan and/zoom toone or more images, change captions, titles or credit styles, changefont settings, add or remove music, add or delete user assets 135 to beincluded in the movie 160, etc.

In an embodiment if the user wishes to edit the movie then the userinputs their edit requests to the movie production system 444. In anaspect of this embodiment the user 145 directs their edits to the themeapplication engine 120 of the movie production system

In an embodiment the newest version of the movie, with user-requestededits implemented, is output to the user for review 448. In an aspect ofthis embodiment the theme application engine 120 of the movie makersystem 100 directs the output of the movie 160 to the user 145 via theUI 180. In an embodiment the movie 160 is in a WYSIWYG formatappropriate for user review.

In an embodiment the movie maker system again, at decision block 430,makes a determination as to whether the user is requesting any edits tothe movie.

If at decision block 430 there are no user-requested movie edits then inan embodiment at decision block 432 a determination is made as towhether the user has introduced new assets to the movie productionsystem for inclusion in a generated movie. If yes, in an embodiment, andreferring back to FIG. 4A, the new user assets are made available to themovie production system 400 and processed as prior introduced userassets were.

Referring again to FIG. 4B if at decision block 432 there are no newuser assets to be included in a generated movie then in an embodiment atdecision block 434 a determination is made as to whether any user assetshave been removed by the user for use in generating a movie. If yes, inan embodiment and referring back to FIG. 4A, the movie production systemexecutes the user-chosen theme script to regenerate, or otherwisemodify, the movie without the previously included user assets 418.

Referring again to FIG. 4B if at decision block 434 no user assets havebeen excluded for use in generating a movie then in an embodiment atdecision block 436 a determination is made as to whether the user hasrequested the movie be published. If no, in an embodiment and referringback to FIG. 4A, the movie maker system continues to output the movie tothe user or otherwise make the movie available to the user for review420.

If at decision block 436 the user has commanded the movie be publishedthen in an embodiment the movie production system encodes the movie intoone or more appropriate output formats 438. In an embodiment the movieproduction system stores the encoded movie 438. In an alternativeembodiment, if at decision block 426 the user has commanded the movie bepublished then in an embodiment the movie production system stores thefinished movie 438. In an alternative embodiment the movie productionsystem thereafter encodes the finished movie into one or more versionsof the finished movie pursuant to requirements for the encoded movie'sdestination 438.

In an embodiment the movie production system can publish, or push, afinished, encoded version of the movie on to one or more indicatedcomputing devices or media 440. In an embodiment the movie productionsystem can publish a finished, encoded version of the movie to one ormore publication points 440.

In an embodiment the movie production system thereafter ends processingfor the current movie 442.

FIGS. 5A-5E illustrate an embodiment logic flow for an embodiment movieproduction system 100 to execute, or otherwise run or act upon, auser-chosen theme script 150 to create a movie 160; i.e., an embodimentlogic flow for the movie production system execution of a theme scriptto generate a movie 418 of FIG. 4A. While the following discussion ismade with respect to systems portrayed herein the operations describedmay be implemented in other systems. The operations described herein arenot limited to the order shown. Additionally, in other alternativeembodiments more or fewer operations may be performed. In any embodimentnot all steps need be performed for each script file 150 and/or thesteps may be performed in a different order for different script files150. Further, the operations depicted may be preformed by an embodimentmovie production system 100 or by an embodiment movie production system100 in combination with one or more other systems.

Referring to FIG. 5A, in an embodiment user assets are chosen, orotherwise identified, to be included in the story, or movie, 500.

In an embodiment, pursuant to one or more theme script rules of the userchosen script file the user assets, or a subset thereof, are groupedinto one or more chapters for a resultant movie 502. In an aspect ofthis embodiment the theme application engine 120 organizes the userassets 135, or a subset thereof, into one or more movie chapters 240. Inan aspect of this embodiment, pursuant to one or more script file rules175, the theme application engine 120 accesses the asset database(s) 170to include modified user assets in the generated movie 160 and accessesthe user assets for those user assets to be included in the generatedmovie 160 that have not, as yet, been modified. In an aspect of thisembodiment the theme application engine 120 chooses the user assets, ormodified user assets, for each chapter 240 based on the available userassets 135, and modified user assets, mined metadata and featureinformation and/or keywords identified in the user-chosen script file150, e.g., SinglePersonShot, GroupShot, CloseUp, etc.

In an embodiment, pursuant to one or more theme script rules of theuser-chosen script file, the user assets are arranged and/or orderedwithin the movie 504. In an aspect of this embodiment, pursuant to oneor more script file rules 175, the theme application engine 120 arrangesand/or orders the user assets 135, and/or modified user assets stored inan asset database 170, within the various movie chapters 240; e.g.,orders the user assets 135 from the first to be displayed to the last tobe displayed for a first chapter 240 of the movie 160, etc.

In an embodiment, pursuant to one or more theme script rules, one ormore user assets are modified 506. In an aspect of this embodiment,pursuant to one or more theme script rules 175, the theme applicationengine 120 signals, or otherwise directs, the adaptation engine 140 totranspose, or modify, one or more user assets 135 to be included in themovie 160. For example, in an aspect of this embodiment and pursuant toone or more theme script rules 175, the theme application engine 120directs the adaptation engine 140 to transpose selected images 105 toblack-and-white.

As another example, in an aspect of this embodiment and pursuant to oneto more theme script rules 175 as well as the length of a user video115, how many other user assets 135 are to be included in the generatedmovie 160, how much the user video changes over x time and/or etc., thetheme application engine 120 can direct the adaptation engine 140 totrim a user asset video 115. In an embodiment a video clip 115 may betrimmed to highlight what is deemed the interesting sections of thevideo clip 115. In an embodiment the selection of the segments of thevideo clip 115 to retain, and those segments to trim, is based onkeywords in one or more rules 175 of the script file 150 and can befacilitated by stored feature information. Thus, in an embodiment thesegments of a video clip 115 that are retained for a movie 160 can varyfrom script theme 150 to script theme 150 based on the keywordsdesignated in any particular script file 150.

In an embodiment, pursuant to one or more theme script rules of theuser-chosen script file, one or more elements to be included in themovie are dynamically generated 508. In an aspect of this embodiment,pursuant to one or more rules 175 of the user-chosen script file 150,the theme application engine 120 dynamically generates elements 155 tobe included in the movie 160 using user assets 135 or modified userassets. For example, in an embodiment and pursuant to one or more themescript rules 175, the theme application engine 120 dynamically generatesone or more frames for the movie 160 that resemble a scrapbook withimages 105 applied thereto and decorated with clip art. In an embodimentthe selection of the user assets 135 and/or portions of the user assets135 included in a dynamically generated element 155 are based onkeywords in one or more script rules 175 and/or stored metadata and/orfeature information.

In an embodiment dynamically generated elements are stored 508. In anaspect of this embodiment the theme application engine 120 stores theelements 155 it dynamically generates in one or more movie assetdatabases 195. In other aspects of this embodiment the theme applicationengine 120 stores the elements 155 it dynamically generates andreferences the stored elements 155 using one or more of a variety ofstorage constructs, including but not limited to, movie asset databases195, tables, lists, linked lists, etc.

In an embodiment, pursuant to one or more rules of the user-chosenscript file the dynamically generated elements are arranged, or ordered,within the movie 508.

In an embodiment at decision block 510 a determination is made as towhether user transitions have been applied to one or more user assets tobe included in the movie; i.e., has the user already applied one or moretransitions to one or more user assets. If yes, in an embodiment themovie production system notifies the user that the user appliedtransitions will be replaced with theme script identified transitions512.

Whether or not the user has previously applied any transitions to anyuser assets, or group of user assets, included in the movie in anembodiment, pursuant to one or more rules of the user-chosen scriptfile, one or more transitions are applied to one or more user assets, orgroups of user assets, and/or one or more dynamically generated elementsincluded in the movie 514. In an aspect of this embodiment pursuant toone or more rules 175 of the user-chosen script file 150 the themeapplication engine 120 applies rule-specified transitions to one or moreuser assets 135, groups of user assets 135, and/or dynamically generatedelements 155 included in the movie 160. In an alternative aspect of thisembodiment the theme application engine 120 signals, or otherwisecommands, the adaptation engine 140 to apply rule-specified transitionsto one or more user assets 135, groups of user assets 135, and/ordynamically generated elements 155 included in the movie 160.

In an aspect of this embodiment some transition applications 514 requireinformation about the user asset(s) a transition is to be applied to,e.g., the portion of an image 105 that the transition is to begin thefade out on. In this aspect of this embodiment the movie productionsystem 100 uses stored metadata, feature and/or analysis information tofinalize the application of a rule-specified transition to one or moreuser assets 135 and/or one or more dynamically generated elements 155.

In an embodiment at decision block 516 a determination is made as towhether user effects have been applied to one or more user assets to beincluded in the movie; i.e., has the user already applied one or moreeffects to one or more user assets. If yes, in an embodiment the movieproduction system notifies the user that the user applied effects willbe replaced with theme script identified effects 518.

Whether or not the user has previously applied any effects to any userassets, or group of user assets, included in the movie in an embodiment,pursuant to one or more rules of the user-chosen script file, one ormore effects are applied to one or more user assets, groups of userassets, and/or one or more dynamically generated elements included inthe movie 520. In an aspect of this embodiment, pursuant to one or morerules 175 of the user-chosen script file 150, the theme applicationengine 120 applies rule-specified effects to one or more user assets135, groups of user assets 135, and/or dynamically generated elements155 included in the movie 160. In an alternative aspect of thisembodiment the theme application engine 120 signals, or otherwisecommands, the adaptation engine 140 to apply rule-specified effects toone or more user assets 135, groups of user assets 135, and/ordynamically generated elements 155 included in the movie 160.

In an aspect of this embodiment some effect applications 520 requireinformation about the user asset an effect is to be applied to, e.g.,the area of interest in an image 105 where the effect is to zoom in on.In this aspect of this embodiment the movie production system 100 usesstored metadata, feature and/or analysis information to finalize theapplication of a rule-specified effect to one or more user assets 135and/or one or more dynamically generated elements 155.

In an embodiment, pursuant to one or more theme script rules of theuser-chosen script file an intro section for the movie is generated 522.In an aspect of this embodiment the theme application engine 120 appliesone or more script rules 175 to generate an intro section 210 for themovie 160. In an embodiment an intro section 210 is generated by thetheme application engine 120 giving special treatment, e.g., transitionand/or effects application, title and/or caption inclusion, etc., to thefirst, or selected first group of, movie frames which may include one ormore user assets 135 and/or one or more dynamically generated elements155.

In an embodiment the theme application engine 120, pursuant to one ormore script rules 175, adds title information, credit information,captions and/or other text information into one or more frames of themovie's intro section 210. In an embodiment the movie production systemuses metadata from one or more metadata databases to complete thetitle(s), credit(s), caption(s) and/or other text within the introsection of the movie 524.

Referring to FIG. 5B, in an embodiment at decision block 530 adetermination is made as to whether there is adequate metadata tocomplete the intro section of the movie. If no, in an embodiment themovie production system uses generic title(s), generic credit(s) and/orgeneric caption(s) and/or other generic text in place of user assetspecific information within the intro section of the movie for thosetitles, credits, captions and other intro section text for which thereis insufficient metadata 532. In an embodiment the movie productionsystem sets an indication, e.g., a flag, a counter, etc., as anotification that user input for generic text within the intro sectionof the movie is to be requested 534.

Whether or not there is sufficient metadata to complete the textportions of the intro section of the movie in an embodiment, pursuant toone or more theme script rules of the user-chosen script file, an introsection for one or more chapters of the movie is generated 536. In anaspect of this embodiment the theme application engine 120 applies oneor more script rules 175 to generate an intro section 210 for one ormore movie chapters 240. In an embodiment an intro section 210 isgenerated by the theme application engine 120 giving special treatment,e.g., transition and/or effects application, title and/or captioninclusion, etc., to the first, or selected first group, of movie framesof each chapter 240 which may include one or more user assets 135 and/orone or more dynamically generated elements 155.

In an embodiment the theme application engine 120, pursuant to one ormore script rules 175, adds title information, credit information and/orother text information into one or more frames of the intro section 210for one or more movie chapters 240. In an embodiment the movieproduction system uses metadata from one or more metadata databases tocomplete the title(s), credit(s) and any caption and/or other textwithin the intro section of the chapters of the movie 538.

In an embodiment at decision block 540 a determination is made as towhether there is adequate metadata to complete the intro section for thechapters of the movie. If no, in an embodiment the movie productionsystem uses generic title(s), generic credit(s) and/or genericcaption(s) and/or other generic text in place of user asset specificinformation within the intro section of the movie chapters for thosetitles, credits, captions and other intro section text for which thereis insufficient metadata 542. In an embodiment the movie productionsystem sets an indication, e.g., a flag, a counter, etc., as anotification that user input for generic text within the one or moreintro sections of one or more movie chapters is to be requested 544.

In an embodiment, pursuant to one or more theme script rules of theuser-chosen script file, an outro section for the movie is generated546. In an aspect of this embodiment the theme application engine 120applies one or more script rules 175 to generate an outro section 230for the movie 160. In an embodiment an outro section 230 is generated bythe theme application engine 120 giving special treatment, e.g.,transition and/or effects application, title and/or caption inclusion,etc., to the last, or last group of, movie frames which may include oneor more user assets 135 and/or one or more dynamically generatedelements 155.

In an embodiment the theme application engine 120, pursuant to one ormore script rules 175, adds title information, credit information,captions and/or other text information into one or more frames of themovie's outro section 230. In an embodiment the movie production systemuses metadata from one or more metadata databases to complete thetitle(s), credit(s), caption(s) and/or other text within the outrosection of the movie 548.

Referring to FIG. 5C, in an embodiment at decision block 550 adetermination is made as to whether there is adequate metadata tocomplete the outro section of the movie. If no, in an embodiment themovie production system uses generic title(s), generic credit(s) and/orgeneric caption(s) and/or other generic text in place of user assetspecific information within the outro section of the movie for thosetitles, credits, captions and other outro section text for which thereis insufficient metadata 552. In an embodiment the movie productionsystem sets an indication, e.g., a flag, a counter, etc., as anotification that user input for generic text within the outro sectionof the movie is to be requested 554.

Whether or not there is sufficient metadata to complete the textportions of the outro section of the movie, in an embodiment, pursuantto one or more theme script rules of the user-chosen script file, anoutro section for one or more chapters of the movie is generated 556. Inan aspect of this embodiment the theme application engine 120 appliesone or more script rules 175 to generate an outro section 230 for one ormore movie chapters 240. In an embodiment an outro section 230 isgenerated by the theme application engine 120 giving special treatment,e.g., transition and/or effects application, title and/or captioninclusion, etc., to the last, or last group of, movie frames of achapter 240 which may include one or more user assets 135 and/or one ormore dynamically generated elements 155.

In an embodiment the theme application engine 120, pursuant to one ormore script rules 175, adds title information, credit information and/orother text information into one or more frames of the outro section 230for one or more chapters 240 of the movie 160. In an embodiment themovie production system uses metadata from one or more metadatadatabases to complete the title(s), credit(s), caption(s) and/or othertext within the outro section of the chapters of the movie 558.

In an embodiment at decision block 560 a determination is made as towhether there is adequate metadata to complete the outro sections forthe chapters of the movie. If no, in an embodiment the movie productionsystem uses generic title(s), generic credit(s) and/or genericcaption(s) and/or other generic text in place of user asset specificinformation within the outro section of the movie chapters for thosetitles, credits, captions and other outro section text for which thereis insufficient metadata 562. In an embodiment the movie productionsystem sets an indication, e.g., a flag, a counter, etc., as anotification that user input for generic text within the one or moreoutro sections of one or more movie chapters is to be requested 564.

In an embodiment, pursuant to one or more theme script rules of theuser-chosen script file, one or more captions are added to the bodysection of the movie 566. In an aspect of this embodiment the themeapplication engine 120 applies one or more script rules 175 to generateone or more captions 230 for one or more movie frames in the bodysection 220 of the movie 160. In an embodiment the movie productionsystem uses metadata from one or more metadata databases to complete thecaptions 566.

Referring to FIG. 5D, in an embodiment at decision block 570 adetermination is made as to whether there is adequate metadata tocomplete the captions for the body of the movie. If no, in an embodimentthe movie production system uses generic captions in place of user assetspecific information for those captions for which there is insufficientmetadata 572. In an embodiment the movie production system sets anindication, e.g., a flag, a counter, etc., as a notification that userinput for generic captions within the body section of the movie is to berequested 574.

Whether or not there is sufficient metadata to personalize the captionsin the movie's body, in an embodiment at decision block 576 adetermination is made as to whether there is user included music for themovie. If no, in an embodiment theme script identified music isincorporated within the movie as dictated by one or more theme scriptrules 578.

If there is user included music for the movie, in an embodiment atdecision block 580 a determination is made as to whether the user wantsto change the music to the theme script identified music. In an aspectof this embodiment the user 145 is asked, via the UI 180, whether themovie production system should use the user included music or themescript identified music for the generated movie 160.

If the user indicates the theme script identified music should beincorporated within the movie then in an embodiment the theme scriptidentified music is added to the movie as dictated by one or more themescript rules 578.

If the user indicates the user included music should be incorporatedwithin the movie then in an embodiment at decision block 582 adetermination is made as to whether there is sufficient user includedmusic for the entire generated movie. If yes, in an embodiment the movieproduction system applies the user included music to the generated movie584. If, however, there is insufficient user included music for theentire generated movie then in an embodiment the movie production systemloops the user included music as dictated by one or more theme scriptrules for the user included music to be applied to the generated movie586. In an alternate embodiment if there is insufficient user includedmusic for the entire generated movie then the movie production systemapplies user included music for the portions of the movie where userincluded music is available and applies theme script identified musicfor other portions of the generated movie 586.

Referring to FIG. 5E, in an embodiment at decision block 590 adetermination is made as to whether user input is required to completethe movie; e.g., are there one or more generic captions or titles, etc.,that require user input because the necessary metadata was unavailable.If yes, in an embodiment the movie production system prompts the user toinput information in order to complete the movie 592. In an aspect ofthis embodiment the theme application engine 120, via the UI 180,prompts the user 145 to input information to fill in blank captionsand/or replace generic information in captions, titles and/or creditswith personal information to complete the movie 160.

In an embodiment the movie production system includes the user-providedinformation in the movie as directed by one or more theme script rules594. In an aspect of this embodiment the theme application engine 120 ofthe movie production system 100 includes the user-provided informationin the movie 160 as directed by one or more theme script rules 175.

In an embodiment a movie has been automatically generated and processingof the user-chosen script file is ended 596.

In an embodiment if one or more additional user assets 135 are includedby the user 145 for use in generating a movie 160 or one or more userassets 135 are removed by the user 145 for use in generating a movie 160then various steps of FIGS. 5A to 5E are performed as appropriate on thenew set of user assets for generation of a movie 160. For example, if anew video 115 is added by the user 145 to the set of user assets 135 tobe used for a movie 160 the movie production system 100 automaticallyorganizes the video 115 within the movie 160 and applies one or moretransitions and/or one or more effects to the video frames as dictatedby the theme script rules 175.

While in embodiments discussed herein tasks have been assigned tovarious identified components of an embodiment movie production system100, in other embodiments the described tasks can be performed by otherand/or additional system components.

Computing Device System Configuration

FIG. 6 is a block diagram that illustrates an exemplary computing devicesystem 600 upon which an embodiment can be implemented. The computingdevice system 600 includes a bus 605 or other mechanism forcommunicating information, and a processing unit 610 coupled with thebus 605 for processing information. The computing device system 600 alsoincludes system memory 615, which may be volatile or dynamic, such asrandom access memory (RAM), non-volatile or static, such as read-onlymemory (ROM) or flash memory, or some combination of the two. The systemmemory 615 is coupled to the bus 605 for storing information andinstructions to be executed by the processing unit 610, and may also beused for storing temporary variables or other intermediate informationduring the execution of instructions by the processing unit 610. Thesystem memory 615 often contains an operating system and one or moreprograms, and may also include program data.

In an embodiment, a storage device 620, such as a magnetic or opticaldisk, is also coupled to the bus 605 for storing information, includingprogram code consisting of instructions and/or data.

The computing device system 600 generally includes one or more displaydevices 635, such as, but not limited to, a display screen, e.g., acathode ray tube (CRT) or liquid crystal display (LCD), a printer, andone or more speakers, for providing information to a computing deviceuser. The computing device system 600 also generally includes one ormore input devices 630, such as, but not limited to, a keyboard, mouse,trackball, pen, voice input device(s), and touch input devices, which acomputing device user can use to communicate information and commandselections to the processing unit 610. All of these devices are known inthe art and need not be discussed at length here.

The processing unit 610 executes one or more sequences of one or moreprogram instructions contained in the system memory 615. Theseinstructions may be read into the system memory 615 from anothercomputing device-readable medium, including, but not limited to, thestorage device 620. In alternative embodiments, hard-wired circuitry maybe used in place of or in combination with software programinstructions. The computing device system environment is not limited toany specific combination of hardware circuitry and/or software.

The term “computing device-readable medium” as used herein refers to anymedium that can participate in providing program instructions to theprocessing unit 610 for execution. Such a medium may take many forms,including but not limited to, storage media and transmission media.Examples of storage media include, but are not limited to, RAM, ROM,EEPROM, flash memory, CD-ROM, digital versatile disks (DVD), magneticcassettes, magnetic tape, magnetic disk storage, or any other magneticmedium, floppy disks, flexible disks, punch cards, paper tape, or anyother physical medium with patterns of holes, memory chip, or cartridge.The system memory 615 and storage device 620 of the computing devicesystem 600 are further examples of storage media. Examples oftransmission media include, but are not limited to, wired media such ascoaxial cable(s), copper wire and optical fiber, and wireless media suchas optic signals, acoustic signals, RF signals and infrared signals.

The computing device system 600 also includes one or more communicationconnections 650 coupled to the bus 605. The communication connection(s)650 provide a two-way data communication coupling from the computingdevice system 600 to other computing devices on a local area network(LAN) 665 and/or wide area network (WAN), including the World Wide Web,or Internet 670. Examples of the communication connection(s) 650include, but are not limited to, an integrated services digital network(ISDN) card, modem, LAN card, and any device capable of sending andreceiving electrical, electromagnetic, optical, acoustic, RF or infraredsignals.

Communications received by the computing device system 600 can includeprogram instructions and program data. The program instructions receivedby the computing device system 600 may be executed by the processingunit 610 as they are received, and/or stored in the storage device 620or other non-volatile storage for later execution.

CONCLUSION

While various embodiments are described herein, these embodiments havebeen presented by way of example only and are not intended to limit thescope of the claimed subject matter. Many variations are possible whichremain within the scope of the following claims. Such variations areclear after inspection of the specification, drawings and claims herein.Accordingly, the breadth and scope of the claimed subject matter is notto be restricted except as defined with the following claims and theirequivalents.

What is claimed is:
 1. A method for automated story generation, themethod comprising: analyzing a group of one or more assets to minemetadata and feature information from the group of assets; analyzing thegroup of assets to determine if any corrections are required for any ofthe assets; rendering at least one correction to at least one asset ofthe group of assets wherein an asset that is corrected is a correctedasset; storing the corrected assets; applying, by a computing device,rules of a theme script to at least one asset of the group of assets togenerate a story; applying rules of a theme script to at least onecorrected asset to generate the story; creating an intro section for thegenerated story that begins the generated story pursuant to at least onerule of the theme script, wherein the intro section comprises a titlecomprising metadata mined from at least one asset from the group ofassets; creating an outro section for the generated story comprising atleast one final frame of the generated story, wherein the outro sectionis created pursuant to at least one rule of the theme script and whereinthe outro section further comprises a credit comprising metadata minedfrom at least one asset from the group of assets; generating a firstcaption for at least one frame of a first group of frames of thegenerated story pursuant to at least one rule of the theme scriptwherein the first caption comprises text comprising metadata mined fromat least one asset of the group of assets; and generating a secondcaption for at least one frame of a second group of frames of thegenerated story pursuant to at least one rule of the theme scriptwherein the second caption is automatically generated with generic textand wherein the generic text is thereafter replaced with text createdfrom input received from a user; outputting the generated story;encoding the generated story; storing the generated story; andpublishing the generated story.
 2. The method for automated storygeneration of claim 1 wherein publishing the generated story comprisespushing the generated story to at least one device.
 3. The method forautomated story generation of claim 1 wherein publishing the generatedstory comprises publishing the generated story to at least onepublication point.
 4. The method for automated story generation of claim1, further comprising dynamically creating an element for the generatedstory wherein the element comprises at least one asset from the group ofassets.
 5. The method for automated story generation of claim 1, furthercomprising: identifying at least two assets from the group of assets tobe story assets that rules of the theme script are applied to generatethe story; grouping the story assets into at least one story chapter;and arranging the story assets grouped in each story chapter in anorder.
 6. The method for automated story generation of claim 5, furthercomprising: creating an intro section for at least one story chapterpursuant to at least one rule of the theme script wherein a createdintro section for a story chapter comprises at least one beginning framefor the story chapter; and creating an outro section for at least onestory chapter pursuant to at least one rule of the theme script whereina created outro section for a story chapter comprises at least one finalframe for the story chapter.
 7. The method for automated storygeneration of claim 1, further comprising including music with at leastone frame of the generated story pursuant to at least one rule of thetheme script.
 8. The method for automated story generation of claim 1wherein outputting the generated story comprises outputting thegenerated story comprising a movie in a wysiwyg format.
 9. The methodfor automated story generation of claim 1 wherein the generated storycomprises a movie.
 10. A method for automated generation of a moviecomprising at least two frames using a theme script comprising at leastone theme script rule, the method comprising: identifying a set of atleast one asset from a group of at least two assets to be movie assetsthat are included in a movie; grouping the movie assets into at leastone chapter for the movie; arranging the movie assets grouped in eachchapter of the movie in an order; generating, by a computing device, anintro section for the movie pursuant to at least one theme script rule;generating an outro section for the movie pursuant to at least one themescript rule; generating a first caption for at least one frame of themovie pursuant to at least one theme script rule wherein the firstcaption comprises text comprising metadata mined from at least one assetof the group of at least two assets; generating a second caption for atleast one frame of the movie pursuant to at least one theme script rulewherein the second caption is automatically generated with generic textand wherein the generic text is thereafter replaced with text createdfrom input received from a user; and outputting the movie in a wysiwygformat.
 11. The method for automated generation of a movie of claim 10,further comprising: automatically encoding the movie; automaticallystoring the encoded movie; upon receiving a command to publish the movieto a device, pushing the movie to the device; and upon receiving acommand to publish the movie to a publication point, publishing themovie to the publication point.
 12. The method for automated generationof a movie of claim 10, further comprising: analyzing the group of atleast two assets to mine metadata from at least one asset of the groupof at least two assets; analyzing the group of at least two assets toidentify at least one correction to be made to at least one asset of thegroup of at least two assets; rendering an identified correction to atleast one asset of the group of at least two assets; storing an assetthat has been corrected; and identifying a stored asset that has beencorrected to be a movie asset included in the movie.
 13. The method forautomated generation of a movie of claim 12, further comprising:automatically generating an intro section for at least one chapter ofthe movie pursuant to at least one theme script rule wherein a generatedintro section for a chapter of the movie comprises at least onebeginning frame for the chapter of the movie and wherein at least onegenerated intro section for a chapter of the movie comprises a titlegenerated from metadata mined from at least one asset of the group of atleast two assets; and automatically generating an outro section for atleast one chapter of the movie pursuant to at least one theme scriptrule wherein a generated outro section for a chapter of the moviecomprises at least one final frame for the chapter of the movie andwherein at least one generated outro section for a chapter of the moviecomprises a credit generated from metadata mined from at least one assetof the group of at least two assets.
 14. The method for automatedgeneration of a movie of claim 10, further comprising: rendering atleast one modification to at least one movie asset pursuant to at leastone theme script rule; and including at least one movie asset that ismodified pursuant to at least one theme script rule within at least onechapter of the movie.
 15. The method for automated generation of a movieof claim 10, further comprising: dynamically generating an element to beincluded in the movie pursuant to at least one theme script rule whereinthe generated element comprises at least one movie asset; and includingthe generated element in a chapter of the movie.
 16. A movie productionsystem for automatically generating stories, the movie production systemcomprising: a computing device configured to automatically apply themescript rules to assets to generate frames for a story; the computingdevice further configured to automatically analyze assets to identifyasset information comprising metadata; the computing device furtherconfigured to automatically analyze assets to identify assetmodification details comprising information on assets to be modified forcorrection; the computing device further configured to automaticallymodify assets without the need for user input; the computing devicefurther configured to automatically generate an introduction section fora story that begins the story, wherein the introduction sectioncomprises a title generated from asset information; the computing devicefurther configured to automatically generate an end section for a storywherein the end section comprises a credit generated from assetinformation; and the computing device further configured to output agenerated story.
 17. The movie production system for automaticallygenerating stories of claim 16, the movie production system furthercomprising: the computing device further configured to receive editingcommands from a user for editing at least one frame of a story; thecomputing device further configured to automatically apply editspursuant to received editing commands to at least one frame of agenerated story to create an updated generated story; and the computingdevice further configured to output the updated generated story.